Related Issue

close #69286

Why

TypeScript SDK users had to run esbuild by hand and hand-write the airflow-metadata.yaml sidecar, which could drift from the bundle.

How

• Add airflow-ts-pack CLI that bundles a TypeScript entrypoint with esbuild and embeds the Airflow metadata into bundle.mjs as a trailing //# airflowMetadata=<base64> comment, producing a single deployable artifact
• Add --airflow-metadata dump mode to startCoordinator() so the manifest comes from the bundle's own task registry, never hand-written
• Update NodeCoordinator to read embedded metadata first, falling back to the airflow-metadata.yaml sidecar for compatibility

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  Claude Code with Fable 5

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.